Multi-access data connection in a mobile network

ABSTRACT

Apparatuses, methods, and systems are disclosed for establishing data paths over multiple access network for a multi-access data connection. One apparatus (400) includes a processor (405) and a transceiver (425) that communicates with one or more network functions in a mobile communication network. The processor (405) receives a first session management request via an AMF. Here, the first session management request contains a second session management request sent by a remote unit that communicates with the mobile communication network over a first access network and a second access network, the second session management request being sent over the second access network. The processor (405) sends a first request to the access management function to establish a first data path for a multi-access data connection over the first access network and sends a second request to the access management function to establish a second data path for the multi-access data connection over the second access network. Here, both the first data path and the second data path are anchored at a common user plane network function in the mobile communication network.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to establishing data pathsover multiple access network for a multi-access data connection.

BACKGROUND

The following abbreviations and acronyms are herewith defined, at leastsome of which are referred to within the following description.

Third Generation Partnership Project (“3GPP”), Positive-Acknowledgment(“ACK”), Access and Mobility Management Function (“AMF”), Binary PhaseShift Keying (“BPSK”), Carrier Aggregation (“CA”), Clear ChannelAssessment (“CCA”), Control Channel Element (“CCE”), Channel StateInformation (“CSI”), Common Search Space (“CSS”), Discrete FourierTransform Spread (“DFT-S”), Downlink Control Information (“DCI”),Discrete Fourier Transform Spread OFDM (“DFT-S-OFDM”), Downlink (“DL”),Downlink Pilot Time Slot (“DwPTS”), Enhanced Clear Channel Assessment(“eCCA”), Enhanced Mobile Broadband (“eMBB”), Evolved Node B (“eNB”),European Telecommunications Standards Institute (“ETSI”), Frame BasedEquipment (“FBE”), Frequency Division Duplex (“FDD”), Frequency DivisionMultiple Access (“FDMA”), Guard Period (“GP”), Hybrid Automatic RepeatRequest (“HARQ”), Internet-of-Things (“IoT”), Key Performance Indicators(“KPI”), Licensed Assisted Access (“LAA”), Load Based Equipment (“LBE”),Listen-Before-Talk (“LBT”), Long Term Evolution (“LTE”), LTA Advanced(“LTE-A”), Medium Access Control (“MAC”), Multiple Access (“MA”),Modulation Coding Scheme (“MCS”), Machine Type Communication (“MTC”),Massive MTC (“mMTC”), Multiple Input Multiple Output (“MIMO”), MultipathTCP (“MPTCP”), Multi User Shared Access (“MUSA”), Narrowband (“NB”),Negative-Acknowledgment (“NACK”) or (“NAK”), Network Function (“NF”),Next Generation Node B (“gNB”), Non-Orthogonal Multiple Access (“NOMA”),Orthogonal Frequency Division Multiplexing (“OFDM”), Primary Cell(“PCell”), Physical Broadcast Channel (“PBCH”), Physical DownlinkControl Channel (“PDCCH”), Physical Downlink Shared Channel (“PDSCH”),Pattern Division Multiple Access (“PDMA”), Physical Hybrid ARQ IndicatorChannel (“PHICH”), Physical Random Access Channel (“PRACH”), PhysicalResource Block (“PRB”), Physical Uplink Control Channel (“PUCCH”),Physical Uplink Shared Channel (“PUSCH”), Quality of Service (“QoS”),Quadrature Phase Shift Keying (“QPSK”), Radio Resource Control (“RRC”),Random Access Procedure (“RACH”), Random Access Response (“RAR”),Reference Signal (“RS”), Resource Spread Multiple Access (“RSMA”), RoundTrip Time (“RTT”), Receive (“RX”), Sparse Code Multiple Access (“SCMA”),Switching/Splitting Function (“SSF”), Scheduling Request (“SR”), SessionManagement Function (“SMF”), Sounding Reference Signal (“SRS”), SingleCarrier Frequency Division Multiple Access (“SC-FDMA”), Secondary Cell(“SCell”), Shared Channel (“SCH”), Signal-to-Interference-Plus-NoiseRatio (“SINR”), System Information Block (“SIB”), Transport Block(“TB”), Transport Block Size (“TBS”), Transmission Control Protocol(“TCP”), Time-Division Duplex (“TDD”), Time Division Multiplex (“TDM”),Transmission and Reception Point (“TRP”), Transmit (“TX”), UplinkControl Information (“UCI”), User Datagram Protocol (“UDP”), UserEntity/Equipment (Mobile Terminal) (“UE”), Uplink (“UL”), UniversalMobile Telecommunications System (“UMTS”), Uplink Pilot Time Slot(“UpPTS”), Ultra-reliability and Low-latency Communications (“URLLC”),and Worldwide Interoperability for Microwave Access (“WiMAX”). As usedherein, “HARQ-ACK” may represent collectively the Positive Acknowledge(“ACK”) and the Negative Acknowledge (“NAK”). ACK means that a TB iscorrectly received while NAK means a TB is erroneously received.

In 5G networks, the core network is to support Multi-Access PDU (MA-PDU)sessions between 3GPP access networks (including LTE, evolved LTE, andNew Radio) and non-3GPP (typically WLAN) access networks. A MA-PDUsession refers to a data session composed of two (and, rarely, of more)PDU sessions that share the same attributes (e.g., the same S-NSSAI,same SSC mode, same DNN, same type, same address/prefix, etc.), but areestablished over different types of access networks (e.g., over a 3GPPAN and a WLAN). These PDU sessions established over different types ofaccess networks are terminated at same UPF anchor (UPF-A).

However, establishing a MA-PDU session currently requires two separateUE-requested PDU sessions. First, an initial PDU session over one accessis established and then an additional PDU over a different access isalso established. The additional PDU session becomes “linked” with theinitial PDU session because it was established to the same APN and alsobecause it contains an Network-Based IP Flow Mobility (“NBIFOM”)indication.

BRIEF SUMMARY

Methods for establishing a multi-access data connection are disclosed.Apparatuses and systems also perform the functions of the methods. Insome embodiments, a method of a session management function forestablishing a multi-access data connection includes receiving a firstsession management request via an access management function in a mobilecommunication network. Here, the first session management requestcontains a second session management request sent by a remote unit incommunication with the mobile communication network over a first accessnetwork and a second access network. The method includes sending a firstrequest to the access management function to establish a first data pathfor the multi-access data connection over the first access network, inresponse to the first session management request. The method includessending a second request to the access management function to establisha second data path for the multi-access data connection over the secondaccess network, wherein both the first data path and the second datapath are anchored at a common user plane network function in the mobilecommunication network, in response to the first session managementrequest. In one embodiment, the second session management request issent over the second access network.

In certain embodiments, a method of a UE for establishing a multi-accessdata connection includes communicating with a mobile communicationnetwork over both a first access network and a second access network andtransmitting a request, over the second access network, to establish adata connection. The method includes receiving a first request to set upa first data bearer for the data connection over the first accessnetwork in response to the request and receiving a second request to setup a second data bearer for the data connection over the second accessnetwork in response to the request, wherein both the first data bearerand the second data bearer are used to carry traffic of the dataconnection.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for establishing a multi-access dataconnection;

FIG. 2 is a block diagram illustrating one embodiment of a networkarchitecture for establishing a multi-access data connection;

FIG. 3 is a schematic block diagram illustrating one embodiment of a UEapparatus for establishing a multi-access data connection;

FIG. 4 is a schematic block diagram illustrating one embodiment of asession management apparatus for establishing a multi-access dataconnection;

FIG. 5A is a block diagram illustrating one embodiment of a networkprocedure for establishing a multi-access data connection;

FIG. 5B is a continuation of the network procedure of FIG. 5A;

FIG. 6A is a block diagram illustrating one embodiment of a networkprocedure for establishing a multi-access data connection;

FIG. 6B is a continuation of the network procedure of FIG. 6A;

FIG. 7 is a block diagram illustrating one embodiment of a networkprocedure for establishing a multi-access data connection;

FIG. 8 is a block diagram illustrating one embodiment of a UE with amulti-access data connection;

FIG. 9 is a schematic flow chart diagram illustrating one embodiment ofa method for establishing a multi-access data connection; and

FIG. 10 is a schematic flow chart diagram illustrating anotherembodiment of a method for establishing a multi-access data connection.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects.

For example, the disclosed embodiments may be implemented as a hardwarecircuit comprising custom very-large-scale integration (“VLSI”) circuitsor gate arrays, off-the-shelf semiconductors such as logic chips,transistors, or other discrete components. The disclosed embodiments mayalso be implemented in programmable hardware devices such as fieldprogrammable gate arrays, programmable array logic, programmable logicdevices, or the like. As another example, the disclosed embodiments mayinclude one or more physical or logical blocks of executable code whichmay, for instance, be organized as an object, procedure, or function.

Furthermore, embodiments may take the form of a program product embodiedin one or more computer readable storage devices storing machinereadable code, computer readable code, and/or program code, referredhereafter as code. The storage devices may be tangible, non-transitory,and/or non-transmission. The storage devices may not embody signals. Ina certain embodiment, the storage devices only employ signals foraccessing code.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random-access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. This code may be provided to a processor of ageneral-purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the schematic flowchartdiagrams and/or schematic block diagrams.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus, orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theschematic flowchart diagrams and/or schematic block diagram.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods, and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, segment, or portion of code, which includes one ormore executable instructions of the code for implementing the specifiedlogical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

Methods, apparatuses, and systems are disclosed to allow a UE toestablish a Multi-Access PDU (MA-PDU) session, or other multi-accessdata connection, by sending a single Session Management (SM) requestmessage towards the mobile communication network. As described herein,the establishment of a multi-access data connection may be UE initiatedor network initiated. Although a MA-PDU session is commonly used as anexample to describe the establishment of the multi-access dataconnection, other types of multi-access data connection may beestablished using the disclosed methods, apparatuses, systems, andprocedures.

FIG. 1 depicts a wireless communication system 100 for establishing amulti-access data connection, according to embodiments of thedisclosure. In one embodiment, the wireless communication system 100includes at least one remote unit 105, a 3GPP access network 120containing at least one cellular base unit 125, a non-3GPP accessnetwork 130, 3GPP communication links 123, non-3GPP access communicationlinks 133, and a mobile core network 140. Even though a specific numberof remote units 105, 3GPP access networks 120, base units 125, 3GPPcommunication links 123, non-3GPP access networks 130, non-3GPPcommunication links 133, and mobile core networks 140 are depicted inFIG. 1, one of skill in the art will recognize that any number of remoteunits 105, 3GPP access networks 120, base units 125, 3GPP communicationlinks 123, non-3GPP access networks 130, non-3GPP communication links133, and mobile core networks 140 may be included in the wirelesscommunication system 100.

In one implementation, the wireless communication system 100 iscompliant with the 5G system specified in the 3GPP specifications. Moregenerally, however, the wireless communication system 100 may implementsome other open or proprietary communication network, for example, LTEor WiMAX, among other networks. The present disclosure is not intendedto be limited to the implementation of any particular wirelesscommunication system architecture or protocol.

In one embodiment, the remote units 105 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), smart appliances (e.g.,appliances connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), or thelike. In some embodiments, the remote units 105 include wearabledevices, such as smart watches, fitness bands, optical head-mounteddisplays, or the like. Moreover, the remote units 105 may be referred toas subscriber units, mobiles, mobile stations, users, terminals, mobileterminals, fixed terminals, subscriber stations, UE, user terminals, adevice, or by other terminology used in the art. The remote units 105may communicate directly with one or more of the base units 125 viauplink (“UL”) and downlink (“DL”) communication signals. Furthermore,the UL and DL communication signals may be carried over the 3GPPcommunication links 123. Similarly, the remote units 105 may communicatewith one or more non-3GPP access networks 130 via UL and DLcommunication signals carried over the non-3GPP communication links 133.

In some embodiments, the remote units 105 communicate with a remote host155 via a network connection with the mobile core network 140. Forexample, a remote unit 105 may establish a PDU connection (or other dataconnection) with the mobile core network 140 using a 3GPP access network120 and/or a non-3GPP access network 130. The mobile core network 140then relays traffic between the remote unit 105 and the remote host 155using the PDU connection. In other embodiments, the remote unit 105 maycommunicate with the remote host 155 over the non-3GPP access network130 without traffic passing through the mobile core network 140. This isreferred to as direct offloading.

The base units 125 may be distributed over a geographic region. Incertain embodiments, a base unit 125 may also be referred to as anaccess terminal, a base, a base station, a Node-B, an eNB, a gNB, a HomeNode-B, a relay node, a device, or by any other terminology used in theart. The base units 125 are generally part of a radio access network(“RAN”), such as the 3GPP access network 120, that may include one ormore controllers communicably coupled to one or more corresponding baseunits 125. These and other elements of radio access network are notillustrated but are well known generally by those having ordinary skillin the art. The base units 125 connect to the mobile core network 140via the 3GPP access network 120.

The base units 125 may serve a number of remote units 105 within aserving area, for example, a cell or a cell sector via a wirelesscommunication link. The base units 125 may communicate directly with oneor more of the remote units 105 via communication signals. Generally,the base units 125 transmit downlink (“DL”) communication signals toserve the remote units 105 in the time, frequency, and/or spatialdomain. Furthermore, the DL communication signals may be carried overthe 3GPP communication links 123. The 3GPP communication links 123 maybe any suitable carrier in licensed or unlicensed radio spectrum. The3GPP communication links 123 facilitate communication between one ormore of the remote units 105 and/or one or more of the base units 125.

The non-3GPP access networks 130 may be distributed over a geographicregion. Each non-3GPP access network 130 may serve a number of remoteunits 105 with a serving area. Typically, a serving area of the non-3GPPaccess network 130 is smaller than the serving area of a base unit 125.The non-3GPP access networks 130 may communicate directly with one ormore remote units 105 by receiving UL communication signals andtransmitting DL communication signals to serve the remote units 105 inthe time, frequency, and/or spatial domain. Both DL and UL communicationsignals are carried over the non-3GPP communication links 133. The 3GPPcommunication links 123 and non-3GPP communication links 133 may employdifferent frequencies and/or different communication protocols. Anon-3GPP access network 130 may communicate using unlicensed radiospectrum. The mobile core network 140 may provide services to a remoteunit 105 via the non-3GPP access networks 130, as described in greaterdetail herein.

In some embodiments, a non-3GPP access network 130 connects to themobile core network 140 via a non-3GPP interworking function (“N3IWF”)135. The N3IWF 135 provides interworking between a non-3GPP AN 120 andthe mobile core network 140, supporting connectivity via the “N2” and“N3” interfaces. As depicted, both the 3GPP access network 120 and theN3IWF 135 communicate with the AMF 145 using a “N2” interface and withthe UPFs 141, 142 using a “N3” interface.

In certain embodiments, a non-3GPP access network 130 may be controlledby an operator of the mobile core network 140 and may have direct accessto the mobile core network 140. Such a non-3GPP AN deployment isreferred to as a “trusted non-3GPP access network.” A non-3GPP accessnetwork 130 is considered as “trusted” when it is operated by the 3GPPoperator, or a trusted partner, and supports certain security features,such as strong air-interface encryption. While the N3IWF 135 is depictedas being located outside both the non-3GPP access network 130 and thecore network 140, in other embodiments the N3IWF 135 may be co-locatedwith the non-3GPP access network 130 (e.g., if the non-3GPP accessnetwork 130 is a trusted non-3GPP access network) or located within thecore network 140.

In one embodiment, the mobile core network 140 is a 5G core (“5GC”) orthe evolved packet core (“EPC”), which may be coupled to another datanetwork 150, like the Internet and private data networks, among otherdata networks. Each mobile core network 140 belongs to a single publicland mobile network (“PLMN”). The present disclosure is not intended tobe limited to the implementation of any particular wirelesscommunication system architecture or protocol.

The mobile core network 140 includes several network functions (“NFs”).As depicted, the mobile core network 140 includes multiple user planefunctions (“UPFs”). Here, the mobile core network 140 includes a firstUPF 141 that serves a 3GPP access network 120, a second UPF 142 thatserves a non-3GPP access network 130, and an anchor UPF (“UPF-A”) 143.The mobile core network 140 also includes multiple control planefunctions including, but not limited to, an Access and MobilityManagement Function (“AMF”) 145, a Session Management Function (“SMF”)146, a Policy Control Function (“PCF”) 148, and a Unified DataManagement function (“UDM”) 149. Although specific numbers and types ofnetwork functions are depicted in FIG. 1, one of skill in the art willrecognize that any number and type of network functions may be includedin the mobile core network 140.

As depicted, a remote unit 105 may be connected to both a base unit 125in a 3GPP access network 120 and a base unit (not shown in FIG. 1) in anon-3GPP access network 130. The remote unit 105 may transmit a requestto establish a data connection over one of the 3GPP access network 120and the non-3GPP access network 130. In some embodiments, the requestincludes an indication that a multi-access data connection is to beestablished (e.g., a UE-initiated multi-access data connection). Forexample, the remote unit 105 may indicate that a multi-access dataconnection is to be established by including a first session identifier(e.g., associated with the 3GPP access network 120) and a second sessionidentifier (e.g., associated with the non-3GPP access network 130) inthe establishment request. As another example, the remote unit 105 mayindicate that a multi-access data connection is to be established byincluding a session identifier and a multi-access parameter in therequest. In other embodiments, the request does not include anindication that a multi-access data connection is to be established(i.e. it is a request for a single-access data connection) but the SMF146 receiving the request determines to create a multi-access dataconnection (e.g., a network-initiated multi-access data connection).

After receiving the request to establish a data connection, the SMF 146initiates the multi-access data connection by triggering theestablishment of a data path (e.g., a child PDU session) over thenon-3GPP access network 130 and triggering the establishment of anotherdata path (e.g., another child PDU session) over the 3GPP access network120. For example, the SMF 146 may trigger the establishment of a datapath by sending a session management (“SM”) request to the AMF 145, asdescribed below with reference to FIGS. 5-7. Note that the multi-accessdata connection is anchored at a common UPF (e.g., the UPF-A 143).

FIG. 2 depicts a network architecture 200 used for establishing amulti-access data connection, according to embodiments of thedisclosure. The network architecture 200 may be a simplified embodimentof the wireless communication system 100. As depicted, the networkarchitecture 200 includes a UE 205 that communicates with mobilecommunication network 210 over both a 5G RAN 215 and a WLAN 220, such asa Wi-Fi RAN. The 5G RAN 215 is one embodiment of the 3GPP access network120 and the WLAN 220 is one embodiment of the non-3GPP access network130, described above. The mobile communication network 210 is oneembodiment of the core network 140, described above, and includes afirst UPF 141, a second UPF 142, an anchor UPF 143, an AMF 145, and aSMF 146. The WLAN 220 accesses the mobile communication network via theN3IWF 135, which may be co-located with the WLAN 220, located in themobile core network, or located outside both the WLAN 220 and the mobilecore network, as described above. The N3IWF 135 communicates with theAMF 145 via an “N2” interface and with the second UPF 142 via an “N3”interface. The 5G RAN 215 communicates with the AMF 145 via an “N2”interface and with the first UPF 141 via an “N3” interface.

As depicted, the UE 205 includes a protocol stack containing an IP layer201, a virtual interface layer 203, a WLAN interface 207, and a 5G radiointerface 209. After sending the single request to establish a dataconnection (e.g., a MA-PDU session), as described herein, the UE 205receives a request to set up a first data bearer for the data connection(corresponding to the first child PDU session 225) over the 5G RAN 215and a request to set up a second data bearer for the data connection(corresponding to the second child PDU session 230) over the WLAN 220.The requests include one or more session identifiers included in thesingle request so that the UE 205 knows they are both for the sameMA-PDU session.

Accordingly, the UE 205 establishes a multi-access data connection (heredepicted as a MA-PDU session) that has two child PDU sessions: a firstchild PDU session 225 that utilizes the 5G radio interface 209 and the5G RAN 215 and a second child PDU session 230 that utilizes the WLANinterface 207 and the WLAN 220 (e.g. a public Wi-Fi hotspot). The twochild PDU sessions are linked in the UE in the “virtual interface” layer203 which exposes a single IP interface to upper layers (e.g., the IPlayer 201). Accordingly, the two child PDU sessions share the same IPaddress and compose a multi-link data connection between the UE 205 andthe UPF-A 143. FIG. 2 shows a scenario with three UPFs: the first UPF141 interfacing to 5G RAN 215, the second UPF 142 interfacing with N3IWF135, and the anchor UPF 143. However, in other scenarios the UPFs 141,142 may not be required, for example where it is possible to interfacethe anchor UPF 143 directly to the 5G RAN 215 and to the N3IWF 135.

FIG. 3 depicts one embodiment of a UE apparatus 300 that may be used forestablishing a multi-access data connection, according to embodiments ofthe disclosure. The UE apparatus 300 may be one embodiment of the remoteunit 105. Furthermore, the UE apparatus 300 may include a processor 305,a memory 310, an input device 315, a display 320, a first transceiver325, and a second transceiver 330.

The first transceiver 325 communicates with a mobile communicationnetwork (e.g., the mobile core network 140) over a first access network,while the second transceiver 330 communicates with the mobilecommunication network over a second access network. The first and secondaccess networks facilitate communication between the mobile core network140 and the UE apparatus 300. In one embodiment, the first accessnetwork is the 5G RAN 215 or other 3GPP access network 120 and thesecond access network is the WLAN 220 or other non-3GPP access network130. In another embodiment, the second access network is the 5G RAN 215or other 3GPP access network 120 and the first access network is theWLAN 220 or other non-3GPP access network 130. In other embodiments, thefirst access network and second access network may be other types ofaccess networks, the first access network being a different type ofaccess network than the second. Each transceiver 325, 330 may include atleast one transmitter and at least one receiver. Additionally, thetransceivers 325, 330 may support at least one network interface such asan “Uu” interface used for communications between the remote unit 105and the 3GPP access network 120.

The processor 305, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 305 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 305 executes instructions stored in thememory 310 to perform the methods and routines described herein. Theprocessor 305 is communicatively coupled to the memory 310, the inputdevice 315, the display 320, the first transceiver 325, and the secondtransceiver 330.

In some embodiments, the processor 305 transmits a request to establisha data connection. In certain embodiments, the request to establish adata connection comprises an indication to establish the data connectionover both the first and the second access networks. In one embodiment,the indication to establish the data connection over both the first andthe second access networks comprises a first session identifierassociated with the first access network and a second session identifierassociated with the second access network. In another embodiment, theindication to establish the data connection over both the first and thesecond access networks comprises a first session identifier and amulti-access parameter. Here, the first session identifier is associatedto both the first access network and the second access network.

In some embodiments, the processor 305 transmits the request toestablish a data connection over the second access network.Additionally, the request to establish a data connection contains asession identifier associated with the second access network and doesnot contain a session identifier associated with the first accessnetwork. In certain embodiments, the request to establish a dataconnection comprises a mode parameter, the mode parameter containing arequested mode of operation for a multi-access data connection.

In certain embodiments, the first access network is an access networknot defined by 3GPP (“non-3GPP access”) and the second access network isan access network defined by 3GPP (“3GPP access”). In such embodiments,the request to establish a data connection may be a Packet Data Unit(“PDU”) session request.

The processor 305 receives a first request to set up a first data bearerfor the data connection over the first access network in response to therequest also receives a second request to set up a second data bearerfor the data connection over the second access network in response tothe request. Here, both the first data bearer and the second data bearerare used to carry the traffic of the data connection.

In certain embodiments, the request to establish a data connectioncontains a session identifier associated with the second access networkand does not contain an indication to establish the data connection overboth the first and the second access networks. Further, the firstrequest to set up a first data bearer for the data connection over thefirst access network and the second request to set up a second databearer for the data connection over the second access network bothinclude the session identifier associated with the second accessnetwork. In such embodiments, the processor 305 determines that therequest over the second access network to establish a data connectionhas initiated the establishment of a multi-access data connection overthe first access network and the second access network.

The memory 310, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 310 includes volatile computerstorage media. For example, the memory 310 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 310 includes non-volatilecomputer storage media. For example, the memory 310 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 310 includes bothvolatile and non-volatile computer storage media. In some embodiments,the memory 310 stores data relating to establishing a multi-access dataconnection, for example storing session identifiers, protocol stacks,security keys, messages, and the like. In some embodiments, the memory310 also stores program code and related data, such as an operatingsystem or other controller algorithms operating on the UE apparatus 300and one or more software applications.

The input device 315, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 315 maybe integrated with the display 320, for example, as a touchscreen orsimilar touch-sensitive display. In some embodiments, the input device315 includes a touchscreen such that text may be input using a virtualkeyboard displayed on the touchscreen and/or by handwriting on thetouchscreen. In some embodiments, the input device 315 includes two ormore different devices, such as a keyboard and a touch panel.

The display 320, in one embodiment, may include any known electronicallycontrollable display or display device. The display 320 may be designedto output visual, audible, and/or haptic signals. In some embodiments,the display 320 includes an electronic display capable of outputtingvisual data to a user. For example, the display 320 may include, but isnot limited to, an LCD display, an LED display, an OLED display, aprojector, or similar display device capable of outputting images, text,or the like to a user. As another, non-limiting, example, the display320 may include a wearable display such as a smart watch, smart glasses,a heads-up display, or the like. Further, the display 320 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the display 320 includes one or more speakersfor producing sound. For example, the display 320 may produce an audiblealert or notification (e.g., a beep or chime). In some embodiments, thedisplay 320 includes one or more haptic devices for producingvibrations, motion, or other haptic feedback. In some embodiments, allor portions of the display 320 may be integrated with the input device315. For example, the input device 315 and display 320 may form atouchscreen or similar touch-sensitive display. In other embodiments,the display 320 may be located near the input device 315. In certainembodiments, the UE apparatus 300 may not include any input device 315and/or display 320.

As discussed above, the first transceiver 325 communicates with a mobilecommunication network via a first access network, while the secondtransceiver 330 communicates with the mobile communication network via asecond access network. The transceivers 325 and 330 operate under thecontrol of the processor 305 to transmit messages, data, and othersignals and also to receive messages, data, and other signals. Forexample, the processor 305 may selectively activate one or both of thetransceivers 325, 330 (or portions thereof) at particular times in orderto send and receive messages. The first transceiver 325 may include oneor more transmitters and one or more receivers for communicating overthe first access network. Similarly, the second transceiver 330 mayinclude one or more transmitters and one or more receivers forcommunicating over the second access network. As discussed above, thefirst transceiver 325 and the second transceiver 330 may support one ormore the network interfaces for communicating with the mobilecommunication network.

FIG. 4 depicts one embodiment of a session management apparatus 400 thatmay be used for establishing a multi-access data connection, accordingto embodiments of the disclosure. The session management apparatus 400may be one embodiment of the SMF 146. Furthermore, the sessionmanagement apparatus 400 may include a processor 405, a memory 410, aninput device 415, a display 420, and a transceiver 425. In someembodiments, the input device 415 and the display 420 are combined intoa single device, such as a touchscreen. In certain embodiments, thesession management apparatus 400 may not include any input device 415and/or display 420.

As depicted, the transceiver 425 includes at least one transmitter 430and at least one receiver 435. Additionally, the transceiver 425 maysupport at least one network interface 440 such as an “Na” interfaceused for communications between a UE and the session managementapparatus 400. Here, the network interface 440 facilitates communicationwith a network function such as the AMF 145, PCF 148 and/or UDM 149.Additionally, the at least one network interface 440 may include an“N11” interface used for communications with an AMF, an “N4” interfaceused for communication with an UDM, and the like.

The processor 405, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 405 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 405 executes instructions stored in thememory 410 to perform the methods and routines described herein. Theprocessor 405 is communicatively coupled to the memory 410, the inputdevice 415, the display 420, and the transceiver 425.

In some embodiments, the processor 405 receives a first sessionmanagement (“SM”) request via an access management function. Here, thefirst SM request contains a second SM request sent by a remote unit(e.g., the second SM request being embedded in the first SM request).The remote unit communicates with the mobile communication network overa first access network and a second access network and has simultaneousconnections over both access networks. In one embodiment, the remoteunit sends the second SM message over the first access network. Inanother embodiment, the remote unit sends the second SM message over thesecond access network. In one embodiment, the second SM message includesa mode parameter, the mode parameter containing a requested mode ofoperation for a multi-access data connection.

In response to the first session management request, the processor 405sends a first request to the access management function to establish afirst data path for a multi-access data connection over the first accessnetwork. In some embodiments, the processor 405 determines to form themulti-access data connection based on the contents of the first SMrequest. For example, the first SM request may include a multi-accessparameter or a specific request for a multi-access data connection. Asanother example, the processor 405 may determine to form themulti-access data connection in response to a need to offload datatraffic to a non-3GPP access network.

The processor 405 also sends a second request to the access managementfunction to establish a second data path for the multi-access dataconnection over the second access network, in response to the firstsession management request, wherein both the first data path and thesecond data path are anchored at a common user plane network function inthe mobile communication network. In some embodiments, establishment ofthe first and second data paths may occur simultaneously.

Where establishment is sequential, the first established data path (intime) is determined based on the access network used by the remote unitto send the second SM request. For example, where the second SM messageis sent over the first access network, then the second data path overthe second access network will be established prior to the first datapath. As another example, where the second SM message is sent over thesecond access network, then the first data path over the first accessnetwork will be established prior to the second data path.

In some embodiments, the first session management request (e.g.,received from the AMF) contains an indication to establish amulti-access data connection for the remote unit over both a firstaccess network and a second access network. For example, indication toestablish a multi-access data connection for the remote unit over both afirst access network and a second access network may be a first sessionidentifier associated with the first access network and a second sessionidentifier associated with the second access network. As anotherexample, the indication to establish a multi-access data connection forthe remote unit over both a first access network and a second accessnetwork may be a multi-access parameter included with a (single) sessionidentifier.

In certain embodiments, the processor 405 queries a policy controlfunction for at least one of multi-access routing rules and multi-accessQoS rules associated with the remote unit. Here, the multi-access QoSrules comprise QoS rules for the first access network and QoS rules forthe second access network. The multi-access routing rules indicate howto route the traffic of the multi-access data connection across thefirst access network and the second access network. Additionally, theprocessor 405 may send a session establishment request to the commonuser plane function anchoring the first and second data paths, thesession establishment request including the multi-access routing rulesand an indication that the first and second data paths are for amulti-access data connection.

In some embodiments, the second session management request is a requestfrom the remote unit to establish a data connection over a single accessnetwork. Additionally, the first session management request may includean indication that the remote unit has simultaneous connections to boththe first access network and the second access network. In suchembodiments, the processor 405 may determine to establish a multi-accessdata connection in response to receiving the first session managementrequest (and the indication that the remote unit has simultaneousconnections to both the first access network and the second accessnetwork).

In certain embodiments, the processor 405 further queries a datamanagement function (e.g., the UDM 149) to determine whether a networksubscription of the remote unit allows a multi-access connection inresponse to receiving the first session management request. In suchembodiments, the processor 405 may determine to establish a multi-accessdata connection based on the network subscription of the remote unit. Incertain embodiments, the processor 405 further queries a policy controlfunction (e.g., the PCF 148) for at least one of multi-access routingrules and multi-access QoS rules associated with the requested dataconnection in response to receiving the first session managementrequest, and wherein the processor determines to establish themulti-access data connection based on the at least one of multi-accessrouting rules and multi-access QoS rules received from the policycontrol function.

In some embodiments, the first access network is a non-3GPP accessnetwork (e.g., an access network not defined by 3GPP) and the secondaccess network is a 3GPP network (e.g., an access network defined by3GPP). Further, the second SM request (e.g., sent by the remote unit)may be a PDU session establishment request. In such embodiment, thesending the first request to the AMF to establish the first data pathfor the multi-access data connection may include the processor 405sending a third SM request to the AMF without an embedded N1 SessionManagement container, the third SM request indicating that the AMF is tosend it to the first access network.

Additionally, sending the second request to the AMF to establish thesecond data path for the multi-access data connection may include theprocessor 405 sending a response to the first SM request, wherein theresponse contains an embedded N1 Session Management container. Here, theembedded N1 Session Management container includes a response to thesecond SM message. Accordingly, the embedded N1 Session Managementcontainer is sent over the same access network used by the remote unitto send the second SM message. In one embodiment, the N1 SessionManagement container includes a PDU session establishment access messagethat contains multi-access routing rules and multi-accessquality-of-service (“QoS”) rules associated with the multi-access dataconnection.

The memory 410, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 410 includes volatile computerstorage media. For example, the memory 410 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 410 includes non-volatilecomputer storage media. For example, the memory 410 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 410 includes bothvolatile and non-volatile computer storage media. In some embodiments,the memory 410 stores data relating to establishing a multi-access dataconnection, for example storing session identifiers associated with aremote unit, protocol stacks, messages, security keys, multi-accesspolicy rules, and the like. In certain embodiments, the memory 410 alsostores program code and related data, such as an operating system orother controller algorithms operating on the session managementapparatus 400 and one or more software applications.

The input device 415, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 415 maybe integrated with the display 420, for example, as a touchscreen orsimilar touch-sensitive display. In some embodiments, the input device415 includes a touchscreen such that text may be input using a virtualkeyboard displayed on the touchscreen and/or by handwriting on thetouchscreen. In some embodiments, the input device 415 includes two ormore different devices, such as a keyboard and a touch panel.

The display 420, in one embodiment, may include any known electronicallycontrollable display or display device. The display 420 may be designedto output visual, audible, and/or haptic signals. In some embodiments,the display 420 includes an electronic display capable of outputtingvisual data to a user. For example, the display 420 may include, but isnot limited to, an LCD display, an LED display, an OLED display, aprojector, or similar display device capable of outputting images, text,or the like to a user. As another, non-limiting, example, the display420 may include a wearable display such as a smart watch, smart glasses,a heads-up display, or the like. Further, the display 420 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the display 420 includes one or more speakersfor producing sound. For example, the display 420 may produce an audiblealert or notification (e.g., a beep or chime). In some embodiments, thedisplay 420 includes one or more haptic devices for producingvibrations, motion, or other haptic feedback. In some embodiments, allor portions of the display 420 may be integrated with the input device415. For example, the input device 415 and display 420 may form atouchscreen or similar touch-sensitive display. In other embodiments,the display 420 may be located near the input device 415.

The transceiver 425 communicates with one or more network functions of amobile communication network. The transceiver 425 operates under thecontrol of the processor 405 to transmit messages, data, and othersignals and also to receive messages, data, and other signals. Forexample, the processor 405 may selectively activate the transceiver (orportions thereof) at particular times in order to send and receivemessages. The transceiver 425 may include one or more transmitters 430and one or more receivers 435. As discussed above, the transceiver 425may support one or more the network interface 440 for communicating withthe base unit 125.

FIG. 5 depicts a network procedure 500 for establishing a multi-accessdata connection, according to embodiments of the disclosure. The networkprocedure 500 is a UE-initiated procedure for establishing amulti-access data connection from a single UE request to establish adata connection. The network procedure involves the UE 205, the 5G RAN215, the N3IWF 135, the AMF 145, the SMF 146, the first UPF 141, thesecond UPF 142, the anchor UPF 143, and the PCF 148. Here, the UE 205 issimultaneously connected to the mobile communication network via a 3GPPaccess network (here, the 5G RAN 215) and a non-3GPP access network(such as the WLAN 220).

The network procedure 500 begins as the UE 205 wants to establish aMA-PDU session over both access networks and sends a NAS message to AMF145 which includes a “PDU Session Establishment Request” (see operation502). In the embodiments of FIG. 5A, the NAS message is sent over the 5GRAN 215 (e.g., the 3GPP access network), but in other embodiments theNAS message may be sent over the non-3GPP access network. The NASmessage includes also two PDU session identities: a first PDU sessionidentity (ID-1) associated with the 3GPP access network (e.g., includingthe 5G RAN 215) and a second PDU session identity (ID-2) associated withthe non-3GPP access network. This is in contrast to conventional NASmessages sent for PDU session establishment which always contain onlyone PDU session identity.

In certain embodiments, the UE 205 indicates that it wants to establisha MA-PDU over both the 3GPP and non-3GPP access networks by includingwithin the NAS message the two PDU session identities. The NAS messagesent by the UE 205 may also include other information, such as therequested DNN (Data Network Name), the requested slice type, etc. Insome embodiments, the “PDU Session Establishment Request” message mayinclude a mode parameter that indicates the requested mode of operationof the MA-PDU session. For example, the mode parameter may indicate thatthe UE 205 prefers the MA-PDU session to operate in active/standby mode,with the child PDU session over non-3GPP access network to be the“active” child and the child PDU session over the 3GPP access network tobe the “standby” child. As another example, the UE 205 may prefer thechild PDU session over the 3GPP access network to be the “active” childand the child PDU session over the non-3GPP access network to be the“standby” child.

In active/standby mode, all traffic of the MA-PDU session is transferredover the “active” child PDU session while the other child PDU session(the “standby” child) does not carry any traffic. When the “active”child PDU session becomes unavailable in the UE 205 (e.g. due to lack ofradio signal), it becomes the “standby” child and the UE 205 transfersall traffic of the MA-PDU session to the other child PDU session whichbecomes the “active” child. When the network receives traffic from theUE 205 over a “standby” child PDU session, it changes this child PDUsession to “active.” When the MA-PDU session operates in active/standbymode there is no need to apply any multi-access routing rules (discussedbelow).

Next, the AMF 145 selects an SMF 146 and sends a SM Request (e.g., afirst SM request) to the SMF 146 (see operation 504). The SM Requestincludes the “PDU Session Establishment Request” received from the UE205. The SM Request further includes an Access Network Type parameter.Here, this parameter has the value “Access network Type=3GPP” toindicate to the SMF 146 that the PDU Session Establishment Request wasreceived over 3GPP access network (e.g., the 5G RAN 215). Where the PDUSession Establishment Request is received over the non-3GPP accessnetwork, then a value “Access network Type=non-3GPP” is to be used. Inaddition, the SM Request includes the two PDU session identitiesprovided by the UE 205 which further indicate that the UE 205 wants toestablish a MA-PDU session. In certain embodiments, the SM Requestfurther includes a multi-access parameter to indicate whether amulti-access data connection (here a MA-PDU) is to be established. Notethat the multi-access parameter is redundant when the UE 205 providestwo PDU session identities.

The SMF 146 selects a PCF (here PCF 148) and establishes a new sessionwith the selected PCF 148, as normally (see operation 506).Subsequently, the SMF 146 retrieves from the PCF 148 multi-accessrouting rules that should be applied at the UE 205 and at the UPF-A 143in order to determine how to route uplink and downlink trafficrespectively across the two child PDU sessions. These multi-accessrouting rules are also known as “traffic steering rules.” As usedherein, traffic steering rules refer to rules provided to the remoteunits 105 by the mobile core network 103. Traffic steering rules areused by the UE 205 for access selection when initiating a new data flow.As an example, multi-access routing rule may indicate “select child PDUsession #2 for app-x” or “select child PDU session #2 for non-IMStraffic between 9 am and 5 pm.” As another example, a multi-accessrouting rule may steer HTTP traffic to child PDU session #2 andvoice-over-IP traffic to child PDU session #1.

The SMF 146 may also retrieve from the PCF 148 multi-access QoS rules.Multi-access QoS rules include QoS rules that should be applied over the5G RAN 215 (e.g., the 3GPP access network) and QoS rules that should beapplied over non-3GPP access network. The purpose of the QoS rulesapplied over one access network is to enable traffic on this accessnetwork to be transported with different QoS characteristics, e.g.different priority, different guaranteed bit rate, etc.

After communicating with the PCF 148, the SMF 146 begins theestablishment of the user-plane for the child PDU session which utilizesnon-3GPP access network (see operation 508). Here, the SMF 146 sends aSession Establishment Request (see operation 510) to the second UPF 142(serving the N31WF 135) and receives an acknowledgement in response (seeoperation 512). The SMF 146 also sends a Session Establishment Request(see operation 514) to the anchor UPF 143 and receives anacknowledgement in response (see operation 516).

Next, the SMF 146 sends an SM Request to the AMF 145 (see operation 518)with a new parameter “Access network type=non-3GPP” to indicate to theAMF 145 that the included N2 SM Information should be sent to thenon-3GPP access network (and not to the 3GPP access network where the“PDU Session Establishment Request” was received from). Note that thisSM Request message does not contain a NAS message for the UE 205 (thereis no N1 SM Container). This is because the SM Request message is not aresponse to the AMF's earlier SM request (e.g., the UE-initiatedrequest), but it is rather a new SM Request initiated by the SMF 146.

The AMF 145 sends the N2 SM Information, i.e. a PDU Session Requestmessage, to the N3IWF 135 (see operation 520). The PDU Session Requestmessage includes the QoS profile(s) to be applied over non-3GPP accessnetwork, each one determined from the QoS rules to be applied over thenon-3GPP access network, provided by the PCF 148 in operation 506. Also,the N3IWF 135 receives the PDU Session ID-2 that was provided by the UE205 in operation 502 and was associated with the non-3GPP accessnetwork.

In response, the N3IWF 135 establishes one or more IPsec child SecurityAssociations (SAs) with the UE 205 (see operation 522). Each IPsec SAcarries one or multiple QoS flows for the child PDU session establishedover the non-3GPP access network (e.g., the second child PDU session230). Each QoS flow is associated with a QoS profile received by theN3IWF 135 in the PDU Session Request message. The N3IWF 135 then sends aPDU Session Request Acknowledgment message to the AMF 145 (see operation524) and the AMF 145 sends a SM Request Acknowledgment message to theSMF 146 (see operation 526). The SMF 146 also sends a SessionModification Request to the second UPF 142 (see operation 528) andreceives an Acknowledgment message in response (see operation 530).

Continuing at FIG. 5B, the SMF 146 begins the establishment of theuser-plane for the child PDU session over 3GPP (e.g., the first childPDU session 225), which utilizes 3GPP access network (see operation532). Here, the SMF 146 sends a Session Establishment Request (seeoperation 534) to the first UPF 141 (serving the 5G RAN 215) andreceives an acknowledgement in response (see operation 536).

The SMF 146 also sends a second Session Establishment Request to theanchor UPF 143 (see operation 538) and receives a second acknowledgementin response (see operation 540). With the second Session EstablishmentRequest, the SMF 146 provides the multi-access routing rules to theanchor UPF 143 (see operation 538). As discussed above, the anchor UPF143 uses the multi-access routing rules to determine how to routedownlink traffic across the two child PDU sessions. The SMF 146 alsoprovides a “Linked PDU session” parameter that informs the anchor UPF143 to associate the new PDU session with the PDU session establishedbefore (e.g., in operation 514). This parameter indicates that theanchor UPF 143 should consider the identified PDU sessions as child PDUsessions of the same MA-PDU session and apply the multi-access routingrules to route downlink traffic across these child PDU sessions.

Next, the SMF 146 sends an SM Request Acknowledgment message to the AMF145 (see operation 542) to respond to the SM Request in operation 504.The SM Request Acknowledgment message includes N2 SM information for the5G RAN 215 and an N1 SM Container that includes a “PDU SessionEstablishment Accept” message. Here, the “PDU Session EstablishmentAccept” message contains (a) the multi-access QoS rules and (b) themulti-access routing rules to be applied by the UE 205. FIG. 8illustrates how these rules are applied in the UE 205.

Returning to FIG. 5B, the “PDU Session Establishment Accept” message isthe response to the “PDU Session Establishment Request” message sent bythe UE 205 in operation 502. In certain embodiments, the “PDU SessionEstablishment Accept” message may include a mode parameter thatindicates the negotiated mode of operation of the MA-PDU session. Thismode may be the same as or different from the mode requested by the UE205. For example, the UE 205 may request active/standby mode with the“active” child being the child PDU session over the non-3GPP accessnetwork, but the network may decide to change the “active” child to thechild PDU session over the 3GPP access network.

The AMF 145 sends the N2 SM Information, i.e. a PDU Session Requestmessage, to the 5G RAN 215 (see operation 544). The PDU Session Requestmessage includes the QoS profile(s) to be applied over the 5G RAN 215(e.g., the 3GPP access network), each profile determined from the QoSrules to be applied over the 3GPP access network, as provided by the PCF148 in operation 506. Also, the 5G RAN 215 receives the PDU Session ID-1that was provided by the UE 205 in operation 502 and was associated withthe 3GPP access network.

In response, the 5G RAN 215 sends a “PDU session Establishment Accept”message to the UE 205. Also, the 5G RAN 215 and UE 205 establish one ormore Data Radio Bearers (DRBs), each DRB associated with one or multipleQoS rules (e.g., for transferring the traffic matching these QoS rules).Each DRB carries one or multiple QoS flows for the child PDU sessionover the 3GPP access network (e.g., the first child PDU session 225).Each QoS flow is associated with a QoS profile sent to the 5G RAN 215.

The 5G RAN 215 then sends an Acknowledgment message to the AMF 145 (seeoperation 548) and the AMF 145 sends a SM Request message with N2information to the SMF 146 (see operation 550). The SMF 146 then sends aSession Modification Request to the first UPF 141 (see operation 552)and receives an Acknowledgment message in response (see operation 554).The SMF 146 procedure sends a SM Request Acknowledgment message to theAMF 145 and the network procedure 500 ends.

Note that the DRBs established over the 3GPP access network (e.g., the5G RAN 215) serve the same purpose of the child IPsec SAs establishedover non-3GPP access network: they both provide multiple communicationbearers with different QoS characteristics. Also, while FIG. 5 showssequential establishment of the child PDU sessions, in other embodimentsthe two child PDU session are established in parallel.

FIG. 6 depicts a network procedure 600 for establishing a multi-accessdata connection from a single UE 205 request, according to embodimentsof the disclosure. The network procedure 600 is also a UE 205-initiatedprocedure and shares many similarities with the network procedure 500.The network procedure 600 involves the UE 205, the 5G RAN 215, the N3IWF135, the AMF 145, the SMF 146, the first UPF 141, the second UPF 142,the anchor UPF 143, and the PCF 148. Again, the UE 205 is simultaneouslyconnected to the mobile communication network via a 3GPP access network(here, the 5G RAN 215) and a non-3GPP access network (such as the WLAN220).

The network procedure 600 begins as the UE 205 wants to establish aMA-PDU session over both access networks and sends a NAS message to AMF145 which includes a “PDU Session Establishment Request” (see operation602). In the embodiments of FIG. 6A, the NAS message is sent over the 5GRAN 215 (e.g., the 3GPP access network), but in other embodiments theNAS message may be sent over the non-3GPP access network. The NASmessage includes a single PDU session identity and a Multi-accessparameter which indicates that the UE 205 wants to establish amulti-access PDU session. This is in contrast to conventional NASmessages sent for PDU session establishment which lacks a Multi-accessparameter.

The NAS message sent by the UE 205 may also include other information,such as the requested DNN (Data Network Name), the requested slice type,etc. In some embodiments, the “PDU Session Establishment Request”message may include a mode parameter that indicates the requested modeof operation of the MA-PDU session. For example, the mode parameter mayindicate that the UE 205 prefers the MA-PDU session to operate inactive/standby mode, with the child PDU session over non-3GPP accessnetwork to be the “active” child and the child PDU session over the 5GRAN 215 to be the “standby” child. As another example, the UE 205 mayprefer the child PDU session over the 5G RAN 215 to be the “active”child and the child PDU session over the non-3GPP access network to bethe “standby” child.

In active/standby mode, all traffic of the MA-PDU session is transferredover the “active” child PDU session while the other child PDU session(the “standby” child) does not carry any traffic. When the “active”child PDU session becomes unavailable in the UE 205 (e.g. due to lack ofradio signal), it becomes the “standby” child and the UE 205 transfersall traffic of the MA-PDU session to the other child PDU session whichbecomes the “active” child. When the network receives traffic from theUE 205 over a “standby” child PDU session, it changes this child PDUsession to “active.” When the MA-PDU session operates in active/standbymode there is no need to apply any multi-access routing rules (discussedbelow).

Next, the AMF 145 selects an SMF 146 and sends a SM Request (e.g., afirst SM request) to the SMF 146 (see operation 604). The SM Requestincludes the “PDU Session Establishment Request” received from the UE205. The SM Request further includes an Access Network Type parameter.Here, this parameter has the value “Access network Type=3GPP” toindicate to the SMF 146 that the PDU Session Establishment Request wasreceived over 3GPP access network (e.g., the 5G RAN 215). Where the PDUSession Establishment Request is received over the non-3GPP accessnetwork, then a value “Access network Type=non-3GPP” is to be used.

In addition, the SM Request includes the PDU session identity and theMulti-access indicator provided by the UE 205. Note that in the networkprocedure 600 the same PDU session ID is used for both access networks.In certain embodiments, the SM Request further includes a multi-accessparameter to indicate to the SMF 146 whether a multi-access dataconnection (here a MA-PDU) is to be established.

The SMF 146 selects and retrieves from the PCF 148 multi-access routingrules and multi-access QoS rules, as described in operation 506. The SMF146 also begins the establishment of the user-plane for the child PDUsession which utilizes non-3GPP access network (see operation 508),sends a Session Establishment Request (see operation 510) to the secondUPF 142 (serving the N3IWF 135) and receives an acknowledgement inresponse (see operation 512). The SMF 146 also sends a SessionEstablishment Request (see operation 514) to the anchor UPF 143 andreceives an acknowledgement in response (see operation 516).

Next, the SMF 146 sends an SM Request to the AMF 145 (see operation 518)with a new parameter “Access network type=non-3GPP” to indicate to theAMF 145 that the included N2 SM Information should be sent to thenon-3GPP access network (and not to the 3GPP access network where theNAS “PDU Session Establishment Request” was received from). Again, thisSM Request message does not contain a NAS message for the UE 205 (thereis no N1 SM Container) as it is not a response to the AMF's earlier SMrequest.

The AMF 145 sends the N2 SM Information as a PDU Session Request messageto the N3IWF 135 (see operation 620). The PDU Session Request messageincludes the QoS profile(s) to be applied over non-3GPP access network,each one determined from the QoS rules to be applied over the non-3GPPaccess network, provided by the PCF 148 in operation 506. Also, theN3IWF 135 receives the single PDU Session ID that was provided by the UE205 in operation 602.

In response, the N3IWF 135 establishes one or more IPsec child SecurityAssociations (SAs) with the UE 205 (see operation 622). Each IPsec SAcarries one or multiple QoS flows for the child PDU session establishedover the non-3GPP access network (e.g., the second child PDU session230). The N3IWF 135 then sends a PDU Session Request Acknowledgmentmessage to the AMF 145 (see operation 524) and the AMF 145 sends a SMRequest Acknowledgment message to the SMF 146 (see operation 526). TheSMF 146 also sends a Session Modification Request to the second UPF 142(see operation 528) and receives an Acknowledgment message in response(see operation 530).

Continuing at FIG. 6B, the SMF 146 begins the establishment of theuser-plane for the child PDU session over 3GPP (e.g., the first childPDU session 225), which utilizes 3GPP access network (see operation532). Here, the SMF 146 sends a Session Establishment Request (seeoperation 534) to the first UPF 141 (serving the 5G RAN 215) andreceives an acknowledgement in response (see operation 536). The SMF 146also sends a second Session Establishment Request to the anchor UPF 143(see operation 538) and receives a second acknowledgement in response(see operation 540).

Next, the SMF 146 sends an SM Request Acknowledgment message to the AMF145 (see operation 542) to respond to the SM Request in operation 504.The SM Request Acknowledgment message includes N2 SM information for the5G RAN 215 and an N1 SM Container that includes a NAS “PDU SessionEstablishment Accept” message. Here, the NAS “PDU Session EstablishmentAccept” message contains (a) the multi-access QoS rules and (b) themulti-access routing rules to be applied by the UE 205. In certainembodiments, the “PDU Session Establishment Accept” message may includea mode parameter that indicates the negotiated mode of operation of theMA-PDU session. This mode may be the same as or different from the moderequested by the UE 205. For example, the UE 205 may requestactive/standby mode with the “active” child being the child PDU sessionover the non-3GPP access network, but the network may decide to changethe “active” child to the child PDU session over the 3GPP accessnetwork.

The AMF 145 sends the N2 SM Information as a PDU Session Request messageto the 5G RAN 215 (see operation 644). The PDU Session Request messageincludes the QoS profile(s) to be applied over the 5G RAN 215 (e.g., the3GPP access network), each profile determined from the QoS rules to beapplied over the 3GPP access network, as provided by the PCF 148 inoperation 506. Also, the 5G RAN 215 receives the single PDU Session IDthat was provided by the UE 205.

In response, the 5G RAN 215 sends a NAS “PDU session EstablishmentAccept” message to the UE 205. Also, the 5G RAN 215 and UE 205 establishone or more Data Radio Bearers (DRBs), each DRB associated with one ormultiple QoS rules (e.g., for transferring the traffic matching theseQoS rules). Each DRB carries one or multiple QoS flows for the child PDUsession over the 3GPP access network (e.g., the first child PDU session225). Each QoS flow is associated with a QoS profile sent to the 5G RAN215.

The 5G RAN 215 then sends an Acknowledgment message to the AMF 145 (seeoperation 548) and the AMF 145 sends a SM Request message with N2information to the SMF 146 (see operation 550). The SMF 146 then send aSession Modification Request to the first UPF 141 (see operation 552)and receives an Acknowledgment message in response (see operation 554).The SMF 146 procedure sends a SM Request Acknowledgment message to theAMF 145 and the network procedure 600 ends.

Note that the DRBs established over the 3GPP access network (e.g., the5G RAN 215) serve the same purpose of the child IPsec SAs establishedover non-3GPP access network: they both provide multiple communicationbearers with different QoS characteristics. While FIGS. 6A-B showsequential establishment of the child PDU sessions, in other embodimentsthe two child PDU session are established in parallel. Also note thatbecause a single PDU session identity is shared by the child PDUsessions, whenever the UE 205 or the network wants to perform anoperation on a child PDU session (e.g. the change the QoS rules of thechild PDU session #2), both the PDU session identity and thecorresponding access network type are to be provided in order toidentify the appropriate child PDU session.

FIG. 7 depicts a network procedure 700 for establishing a multi-accessdata connection, according to embodiments of the disclosure. The networkprocedure 700 is a network-initiated procedure for establishing amulti-access data connection from a single request to establish a dataconnection. The network procedure involves the UE 205, the 5G RAN 215,the N3IWF 135, the AMF 145, the SMF 146, the first UPF 141, the secondUPF 142, the anchor UPF 143, and the PCF 148. Here, the UE 205 issimultaneously connected to the mobile communication network via a 3GPPaccess network (here, the 5G RAN 215) and a non-3GPP access network(such as the WLAN 220).

The network procedure 700 begins and the UE 205 requests a normal (i.e.single-access network) PDU session (see operation 702). In theembodiments of FIG. 7, the NAS message is sent over the 5G RAN 215(e.g., the 3GPP access network), but in other embodiments the NASmessage may be sent over the non-3GPP access network. The NAS messageincludes a single PDU session identity, but does not contain anyindication that the UE 205 wants to establish a multi-access PDUsession. The NAS message sent by the UE 205 may also include otherinformation, such as the requested DNN (Data Network Name), therequested slice type, etc.

Next, the AMF 145 selects an SMF 146 and sends the SM Request to the SMF146 and includes the new Multi-access parameter to indicate to the SMF146 that the UE 205 is connected both to 3GPP access network and tonon-3GPP access network (704). The SM Request includes the “PDU SessionEstablishment Request” received from the UE 205. The SM Request furtherincludes an Access Network Type parameter. Here, this parameter has thevalue “Access network Type=3GPP” to indicate to the SMF 146 that the PDUSession Establishment Request was received over 3GPP access network(e.g., the 5G RAN 215). Where the PDU Session Establishment Request isreceived over the non-3GPP access network, then a value “Access networkType=non-3GPP” is to be used.

Based on the Multi-access parameter and local information or policy, theSMF 146 decides to establish a MA-PDU session instead of thesingle-access network PDU session requested by the UE 205 (see operation706). This decision may be made when the SMF 146 wants e.g. to offloadsome of the data traffic of the requested PDU session to non-3GPP accessnetwork. For example, when the UE 205 requests in operation 702 toestablish a PDU session over 3GPP access network to the Internet DNN(Data Network Name), the SMF 146 may decide to establish a MA-PDUsession to the Internet DNN so that some Internet traffic can beoffloaded to non-3GPP access network.

Before taking this decision, the SMF 146 may interact with the UDM 149to determine if the UE 205's subscription allows the establishment of anMA-PDU session to the requested DNN. In addition, the SMF 146 may decideto establish an MA-PDU session based on information retrieved from thePCF 148 in operation 708. In this case, the decision to establish aMA-PDU session (e.g., operation 706) is taken after operation 708.

As discussed, the SMF 146 interacts with the PCF 148 (e.g. establishes anew PDU-CAN session) and may retrieve multi-access routing rules thatshould be applied at the UE 205 and at the anchor UPF 143 in order todetermine how to route uplink and downlink traffic respectively acrossthe two child PDU sessions (see operation 708). The SMF 146 may alsoretrieve from PCF multi-access QoS rules, i.e. QoS rules that should beapplied over 3GPP access network and QoS rules that should be appliedover non-3GPP access network.

Next, the SMF 146 begins to establish the child PDU session #2 overnon-3GPP access network, as discussed above in operations 508-518. TheAMF 145 sends to the N3IWF 135 the QoS profile(s) to be applied overnon-3GPP access network, each one determined from the QoS rules to beapplied over non-3GPP access network, provided by PCF. Additionally, theN3IWF 135 receives the single PDU session ID that was provided by the UE205 in step 1.

Next, the UE 205 and the N3IWF 135 establish one or more child IPsec SAs(see operation 722). Based on the received PDU Session ID the UE 205determines that these child IPsec SAs are part of the PDU sessionrequested in operation 702. In other words, the UE 205 determines thatthe network has decided to establish a MA-PDU session instead of therequested single-access network PDU session. The N3IWF 135 then sends aPDU Session Request Acknowledgment message to the AMF 145 (see operation524) and the AMF 145 sends a SM Request Acknowledgment message to theSMF 146 (see operation 526). The SMF 146 also sends a SessionModification Request to the second UPF 142 (see operation 528) andreceives an Acknowledgment message in response (see operation 530).

The network procedure 700 continues by establishing the user-plane forthe child PDU session over 3GPP (e.g., the first child PDU session 225),which utilizes 3GPP access network as depicted in FIG. 6B and describedabove with reference to FIG. 6B. In sum, the SMF 146 sends an SM RequestAcknowledgment message to the AMF 145 (e.g., operation 542), the AMF 145sends a PDU Session Request to the 5G RAN 215 that includes the singlePDU Session ID (operation 644), and the UE 205 and 5G RAN 215 establishDRBs (operation 646).

While the Figures show sequential establishment of the child PDUsessions, in other embodiments the two child PDU session are establishedin parallel. Also note that because a single PDU session identity isshared by the child PDU sessions, whenever the UE 205 or the networkwants to perform an operation on a child PDU session (e.g. the changethe QoS rules of the child PDU session #2), both the PDU sessionidentity and the corresponding access network type are to be provided inorder to identify the appropriate child PDU session.

FIG. 8 depicts a UE model 800, according to embodiments of thedisclosure. The UE model 800 shows the UE 205 after the multi-accessdata connection (e.g., the MA-PDU session) is established. As depicted,the IP layer 201 generates an uplink data (UL data) packet which ispassed to the virtual interface layer 203. As described above, thevirtual interface layer 203 is a layer that exposes a single interfaceto the upper layers, e.g. a single IP interface to the IP layer 201 whenthe MA-PDU session is of IP type. The virtual interface layer 203applies the multi-access routing rules 803 that were received during theestablishment of the MA-PDU session and determines whether the UL datapacket should be routed via the child PDU session over 3GPP access orvia the child PDU session over non-3GPP access.

Each child PDU session has its own QoS rules (e.g., QoS rules fornon-3GPP 805 and QoS rules for 3GPP 807), as shown in FIG. 8. The ULdata packet routed to a child PDU session is first matched against a QoSrule and associated with the QoS Flow Identifier (QFI) of the matchedQoS rule. Then, based on the associated QFI, it is routed to acorresponding DRB (for the 3GPP child PDU session) or to a correspondingchild IPsec SA (for the non-3GPP PDU session).

FIG. 9 depicts a method 900 for establishing a multi-access dataconnection, according to embodiments of the disclosure. In someembodiments, the method 900 is performed by an apparatus, such as theSMF 146 and/or session management apparatus 400. In certain embodiments,the method 900 may be performed by a processor executing program code,for example, a microcontroller, a microprocessor, a CPU, a GPU, anauxiliary processing unit, a FPGA, or the like.

The method 900 begins with receiving 905 a first session managementrequest via an access management function in a mobile communicationnetwork. Here, the first session management request containing a secondsession management request sent by a remote unit that communicates withthe mobile communication network over a first access network and asecond access network. In one embodiment, the second session managementrequest is sent over the second access network.

In some embodiments, the first session management request contains anindication to establish a multi-access data connection for the remoteunit over both a first access network and a second access network. Inone embodiment, the indication to establish a multi-access dataconnection for the remote unit over both a first access network and asecond access network contains a first session identifier associatedwith the first access network and a second session identifier associatedwith the second access network. In another embodiment, the indication toestablish a multi-access data connection for the remote unit over both afirst access network and a second access network contains a firstsession identifier and a multi-access parameter.

In some embodiments, the second session management request is a requestfrom the remote unit to establish a data connection over a single accessnetwork, and the first session management request includes an indicationthat the remote unit has simultaneous connections to both the firstaccess network and the second access network. In such embodiments,receiving 905 the first session management request may includecomprising determining to establish a multi-access data connection inresponse to receiving the first session management request. In certainembodiments, the second session management request includes a modeparameter, the mode parameter containing a requested mode of operationfor the multi-access data connection.

In certain embodiments, receiving 905 the first session managementrequest includes querying a policy control function for at least one of:multi-access routing rules and multi-access QoS rules associated withthe remote unit. Here, the multi-access QoS rules comprise QoS rules forthe first access network and QoS rules for the second access network.The multi-access routing rules indicate how to route the traffic of themulti-access data connection across the first access network and thesecond access network.

In certain embodiments, the first access network is an access networknot defined by 3GPP (“non-3GPP access”) and the second access network isan access network defined by 3GPP (“3GPP access”). In such embodiments,the second session management request may be a Packet Data Unit (“PDU”)session establishment request.

The method 900 includes sending 910 a first request to the accessmanagement function to establish a first data path for the multi-accessdata connection over the first access network, in response to the firstsession management request. In certain embodiments, sending 910 thefirst request to the access management function to establish the firstdata path for the multi-access data connection includes sending a thirdsession management request without an embedded N1 Session Managementcontainer. Here, the third session management request indicates that theaccess management function is to send the first request to the firstaccess network.

In some embodiments, sending 910 the first request to the accessmanagement function includes sending a session establishment request tothe common user plane function anchoring the first and second datapaths, the session establishment request including the multi-accessrouting rules and an indication that the first and second data paths arefor a multi-access data connection.

In one embodiment, sending 910 the first request to the accessmanagement function includes querying a data management function todetermine whether a network subscription of the remote unit allows amulti-access connection in response to receiving the first sessionmanagement request and determining to establish a multi-access dataconnection based on the network subscription of the remote unit. Inanother embodiment, sending 910 a first request to the access managementfunction includes querying a policy control function for at least one ofmulti-access routing rules and multi-access QoS rules associated withthe requested data connection in response to receiving the first sessionmanagement request, and determining to establish the multi-access dataconnection based on the at least one of multi-access routing rules andmulti-access QoS rules received from the policy control function.

The method 900 includes sending 915 a second request to the accessmanagement function to establish a second data path for the multi-accessdata connection over the second access network, in response to the firstsession management request. Here, both the first data path and thesecond data path are anchored at a common user plane network function inthe mobile communication network. In certain embodiments, sending 915the second request to the access management function to establish thesecond data path for the multi-access data connection includes sending aresponse to the first session management request, wherein the responsecontains an embedded N1 Session Management container. In one embodiment,the embedded N1 Session Management container includes a PDU sessionestablishment access message that contains multi-access routing rulesand multi-access quality-of-service (“QoS”) rules associated with themulti-access data connection. The method 900 ends.

FIG. 10 depicts a method 1000 for establishing a multi-access dataconnection, according to embodiments of the disclosure. In someembodiments, the method 1000 is performed by an apparatus, such as theremote unit 105, the UE 205, and/or the UE apparatus 300. In certainembodiments, the method 1000 may be performed by a processor executingprogram code, for example, a microcontroller, a microprocessor, a CPU, aGPU, an auxiliary processing unit, a FPGA, or the like.

The method 1000 begins with communicating 1005 with a mobilecommunication network over both a first access network and a secondaccess network. The method 1000 includes transmitting 1010 a request toestablish a data connection. In some embodiments, the first accessnetwork is an access network not defined by 3GPP (“non-3GPP access”) andthe second access network is an access network defined by 3GPP (“3GPPaccess”). In such embodiment, the request to establish a data connectionmay be a PDU session establishment request. In certain embodiments, therequest to establish a data connection comprises a mode parameter, themode parameter containing a requested mode of operation for amulti-access data connection.

In some embodiments, the request to establish a data connection includesan indication to establish the data connection over both the first andthe second access networks. In one embodiment, the indication toestablish the data connection over both the first and the second accessnetworks comprises a first session identifier associated with the firstaccess network and a second session identifier associated with thesecond access network. In another embodiment, the indication toestablish the data connection over both the first and the second accessnetworks comprises a first session identifier and a multi-accessparameter, wherein the first session identifier is associated to boththe first access network and the second access network.

In certain embodiments, transmitting 1010 the request to establish adata connection comprises transmitting over the second access network.In certain embodiments, the request to establish a data connectioncontains a session identifier associated with the second access networkand does not contain a session identifier associated with the firstaccess network.

The method 1000 includes receiving 1015 a first request to set up afirst data bearer for the data connection over the first access networkin response to the request. In certain embodiments, the first request toset up a first data bearer for the data connection over the first accessnetwork includes the session identifier associated with the secondaccess network. In further embodiments, receiving 1015 the first requestto set up a first data bearer may include determining that the requestover the second access network to establish a data connection hasinitiated the establishment of a multi-access data connection over thefirst access network and the second access network, e.g., determinedbased on the first request including the session identifier associatedwith the second access network.

The method 1000 includes receiving 1020 a second request to set up asecond data bearer for the data connection over the second accessnetwork in response to the request. Here, both the first data bearer andthe second data bearer are used to carry traffic of the data connection.The method 1000 ends.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

1. An apparatus comprising: a transceiver that communicates with one ormore network functions in a mobile communication network; and aprocessor that: receives a first session management request via anaccess management function, the first session management requestcontaining a second session management request sent by a remote unitthat communicates with the mobile communication network over a firstaccess network and a second access network, the second sessionmanagement request being sent over the second access network; sends afirst request to the access management function to establish a firstdata path for a multi-access data connection over the first accessnetwork, in response to the first session management request; and sendsa second request to the access management function to establish a seconddata path for the multi-access data connection over the second accessnetwork, in response to the first session management request, whereinboth the first data path and the second data path are anchored at acommon user plane network function in the mobile communication network.2. The apparatus of claim 1, wherein the first session managementrequest contains an indication to establish a multi-access dataconnection for the remote unit over both a first access network and asecond access network.
 3. The apparatus of claim 2, wherein theindication to establish a multi-access data connection for the remoteunit over both a first access network and a second access networkcontains a first session identifier associated with the first accessnetwork and a second session identifier associated with the secondaccess network.
 4. The apparatus of claim 2, wherein the indication toestablish a multi-access data connection for the remote unit over both afirst access network and a second access network contains a firstsession identifier and a multi-access parameter, wherein the firstsession identifier is associated to both the first access network andthe second access network.
 5. The apparatus of claim 1, wherein theprocessor further queries a policy control function for at least one ofmulti-access routing rules and multi-access quality-of-service (“QoS”)rules associated with the remote unit.
 6. (canceled)
 7. The apparatus ofclaim 5, wherein the processor further sends a session establishmentrequest to the common user plane function anchoring the first and seconddata paths, the session establishment request including the multi-accessrouting rules and an indication that the first and second data paths arefor a multi-access data connection.
 8. The apparatus of claim 1, whereinthe first access network is an access network not defined by 3GPP(“non-3GPP access”) and the second access network is an access networkdefined by 3GPP (“3GPP access”), and wherein the second sessionmanagement request is a Packet Data Unit (“PDU”) session establishmentrequest.
 9. The apparatus of claim 8, wherein sending the first requestto the access management function to establish the first data path forthe multi-access data connection comprises sending a third sessionmanagement request without an embedded N1 Session Management container,the third session management request indicating that the accessmanagement function is to send it to the first access network, andwherein sending the second request to the access management function toestablish the second data path for the multi-access data connectioncomprises sending a response to the first session management request,wherein the response contains an embedded N1 Session Managementcontainer.
 10. The apparatus of claim 9, wherein the N1 SessionManagement container includes a PDU session establishment access messagethat contains multi-access routing rules and multi-accessquality-of-service (“QoS”) rules associated with the multi-access dataconnection.
 11. The apparatus of claim 1, wherein the second sessionmanagement request is a request from the remote unit to establish a dataconnection over a single access network, and the first sessionmanagement request includes an indication that the remote unit hassimultaneous connections to both the first access network and the secondaccess network, wherein the processor further determines to establish amulti-access data connection in response to receiving the first sessionmanagement request.
 12. The apparatus of claim 11, wherein the processorfurther queries a data management function to determine whether anetwork subscription of the remote unit allows a multi-access connectionin response to receiving the first session management request, andwherein the processor determines to establish a multi-access dataconnection based on the network subscription of the remote unit.
 13. Theapparatus of claim 11, wherein the processor further queries a policycontrol function for at least one of multi-access routing rules andmulti-access quality-of-service (“QoS”) rules associated with therequested data connection in response to receiving the first sessionmanagement request, and wherein the processor determines to establishthe multi-access data connection based on the at least one ofmulti-access routing rules and multi-access QoS rules received from thepolicy control function.
 14. The apparatus of claim 1, wherein thesecond session management request comprises a mode parameter, the modeparameter containing a requested mode of operation for the multi-accessdata connection.
 15. A method comprising: receiving a first sessionmanagement request via an access management function in a mobilecommunication network, the first session management request containing asecond session management request sent by a remote unit thatcommunicates with the mobile communication network over a first accessnetwork and a second access network, the second session managementrequest being sent over the second access network; sending a firstrequest to the access management function to establish a first data pathfor a multi-access data connection over the first access network, inresponse to the first session management request; and sending a secondrequest to the access management function to establish a second datapath for the multi-access data connection over the second accessnetwork, in response to the first session management request, whereinboth the first data path and the second data path are anchored at acommon user plane network function in the mobile communication network.16. (canceled)
 17. (canceled)
 18. (canceled)
 19. (canceled) 20.(canceled)
 21. (canceled)
 22. (canceled)
 23. (canceled)
 24. (canceled)25. (canceled)
 26. (canceled)
 27. (canceled)
 28. (canceled)
 29. Anapparatus comprising: a transceiver that communicates with a mobilecommunication network over a first access network and over a secondaccess network; and a processor that: transmits a request, over thesecond access network, to establish a data connection; receives a firstrequest to set up a first data bearer for the data connection over thefirst access network in response to the request; and receives a secondrequest to set up a second data bearer for the data connection over thesecond access network in response to the request, wherein both the firstdata bearer and the second data bearer are used to carry traffic of thedata connection.
 30. The apparatus of claim 29, wherein the request toestablish a data connection comprises an indication to establish thedata connection over both the first and the second access networks. 31.The apparatus of claim 30, wherein the indication to establish the dataconnection over both the first and the second access networks comprisesa first session identifier associated with the first access network anda second session identifier associated with the second access network.32. The apparatus of claim 30, wherein the indication to establish thedata connection over both the first and the second access networkscomprises a first session identifier and a multi-access parameter,wherein the first session identifier is associated with both the firstaccess network and the second access network.
 33. (canceled)
 34. Theapparatus of claim 29, wherein the first access network is an accessnetwork not defined by 3GPP (“non-3GPP access”) and the second accessnetwork is an access network defined by 3GPP (“3GPP access”), andwherein the request to establish a data connection is a Packet Data Unit(“PDU”) session establishment request.
 35. The apparatus of claim 29,wherein the request to establish a data connection comprises a modeparameter, the mode parameter containing a requested mode of operationfor a multi-access data connection.
 36. A method comprising:communicating with a mobile communication network over both a firstaccess network and a second access network; transmitting a request, overthe second access network, to establish a data connection; receiving afirst request to set up a first data bearer for the data connection overthe first access network in response to the request; and receiving asecond request to set up a second data bearer for the data connectionover the second access network in response to the request, wherein boththe first data bearer and the second data bearer are used to carrytraffic of the data connection.
 37. (canceled)
 38. (canceled) 39.(canceled)
 40. (canceled)
 41. (canceled)
 42. (canceled)